Parse Range header values. - #112
Merged
Merged
Conversation
samuel-williams-shopify
force-pushed
the
add-range-header
branch
3 times, most recently
from
August 2, 2026 11:39
8736609 to
51dfa71
Compare
3 tasks
samuel-williams-shopify
force-pushed
the
add-range-header
branch
from
August 2, 2026 11:48
51dfa71 to
10e78be
Compare
samuel-williams-shopify
force-pushed
the
add-range-header
branch
from
August 2, 2026 11:50
10e78be to
5cbb622
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Protocol::HTTP::Header::Rangewith support for byte and extension range units.Rangethrough the defaultProtocol::HTTP::Headerspolicy.Tests
bundle exec bake test(760 tests, 1,537 assertions, 100% coverage).bundle exec bake decode:index:coverage lib(438/438 definitions).Contribution